-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle SIGTERM gracefully in recording #792
Conversation
9896c99
to
93c3b2d
Compare
dc0276d
to
0ff6259
Compare
Gist: https://gist.githubusercontent.com/emersonknapp/2e4053ad46ac63ad5fba61b2253f7c2e/raw/1c849f3a190a25cd3bf3e3aa2d1d8dba0ff9d6af/ros2.repos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
…ot mark as failure - gotta fix Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Signed-off-by: Emerson Knapp <eknapp@amazon.com>
0ff6259
to
fb3e3d1
Compare
* Handle SIGTERM gracefully in recording Signed-off-by: Emerson Knapp <eknapp@amazon.com>
Fixes #791
Allow for graceful shutdown (e.g. create
metadata.yml
) on SIGTERM, the same way we do on Ctrl+C/SIGINT.I've added the signal handler into the
rosbag2_py
layer that acts as the main C-side entrypoint for the process, on the assumption that this feature is desirable for the commandline tool and that, if therosbag2_transport::Recorder
is used in other contexts, they may or may not want to handle SIGTERM in the same way.